Rules Builder

The rules builder is a common interface which provides the ability to define conditional clauses or rules in ASM Core and to perform or automate complex functions.

You can use the rules builder in various areas, including:

• Configuring fields in ASM Designer
• Setting up AI Ops rules
• Mapping fields for updating by Manage CMDB Task transactions
• Mapping fields through the Integration Platform
• Search fields on submission screens in Self Service Portal
• Criteria for IPK Workflow Rules

The Rules Builder allows you to build rules based on the following field types: Text , Numeric, Drop Down, Search Fields, List Box, Checkbox and Date. It can be used on custom fields.

It does not support fields of type Text Area or Multi-Select.

Using the Rules Builder

The Rules Builder window looks much like this when you first open it - .

To build a rule:

1. Provide a name for the rule if you are creating a new rule and the window contains the required field.
2. Select in the editing box.
3. Select to view a list of all possible values from a multi-tiered list. The displayed values depend on the context in which you are using the rules builder.
4. Make your selection (such as Call Priority, User, etc).
5. Select an operator (that is, equal (=), less than (<), greater than (>)) from the list that appears automatically. The operators you can pick depend on the item you selected.
6. Select the final part of the criteria (such as, High, Smith, etc) from the next field.

The items you can select are filtered to show relevant fields of the same data type as the selected field. If an item is not available for selection it is shown in italics, allowing you to expand the next tier in a multi-tier list to choose an item from a lower tier. Only like items are available for selection. For example, if your first criteria is a Group, then you must choose a Group as the final value.

7. Add further criteria by selecting the And, Or or Not buttons.
8. Group your criteria if necessary using the Group button. This will insert parentheses around the selected part of a statement. Those criteria contained within the parentheses are evaluated first and the result then processed as part of the entire statement. Otherwise, Not statements will be evaluated before And, and And before Or.
9. When done select OK to save your rules.

For more examples of building rules in ASM Designer and other areas of ASM Core, refer to the relevant topics.

Top Tips

• Make sure your Rule name is unique.
• Be careful with your logic – don’t make a field required while it is hidden or read-only!
• Rules you create for a screen will also be available for any child screens, should you wish to use them.